The system spawns new instances of “standby mode” session and AAA managers for each active control processor (CP) being used. These mirrored processes require both memory and processing resources, which means that additional hardware may be required to enable this feature (see the Additional Hardware Requirements section).
|
•
|
Task recovery mode: Wherein one or more session manager failures occur and are recovered without the need to use resources on a standby packet processing card. In this mode, recovery is performed by using the mirrored “standby-mode” session manager task(s) running on active packet processing cards. The “standby-mode” task is renamed, made active, and is then populated using information from other tasks such as AAA manager. In case of Task failure, limited subscribers will be affected and will suffer outage only until the task starts back up.
|
|
•
|
Full packet processing card recovery mode: Used when a packet processing card hardware failure occurs, or when a planned packet processing card migration fails. In this mode, the standby packet processing card is made active and the “standby-mode” session manager and AAA manager tasks on the newly activated packet processing card perform session recovery.
|
Important: After a session recovery operation, some statistics, such as those collected and maintained on a per manager basis (AAA Manager, Session Manager, etc.) are in general not recovered, only accounting and billing related information is checkpointed and recovered.|
•
|
HNB-GW: HNB Session over IuH
|
|
•
|
HNB-GW: HNB-CN Session over IuPS and IuCS
|
|
•
|
HNB-GW: SeGW Session IPSec Tunnel
|
Session recovery is not supported for the following functions:
Important: Session Recovery is a licensed Cisco feature. A separate feature license may be required. Contact your Cisco account representative for detailed information on specific licensing requirements. For information on installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations chapter in the System Administration Guide.
Important: Any partially connected calls (for example, a session where HA authentication was pending but has not yet been acknowledged by the AAA server) are not recovered when a failure occurs.
Important: A minimum of four packet processing cards (three active and one standby) per individual chassis is required to use this feature.
Important: The session recovery feature, even when the feature use key is present, is disabled by default on the system.|
Step 1
|
xxx-xx-xxxx - 2TP LAC (PDSN/GGSN/SGSN)
xxx-xx-xxxx - Session Recovery (PDIF/PDSN/GGSN/SGSN)
150000 PDSN/GGSN/SGSN
Important: If the current status of the Session Recovery feature is Disabled, you cannot enable this feature until a license key is installed in the system.|
Step 3
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
|
Step 4
|
After the system has been configured and placed in-service, you should verify the preparedness of the system to support this feature as described in the Viewing Session Recovery Status section.
|
|
Step 1
|
xxx-xx-xxxx - 2TP LAC (PDSN/GGSN/SGSN)
150000 PDSN/GGSN/SGSN
Important: If the current status of the Session Recovery feature is Disabled, you cannot enable this feature until a license key is installed in the system.
Important: This feature does not take effect until after the system has been restarted.|
Step 3
|
Save your configuration as described in the Verifying and Saving Your Configuration. chapter of this guide.
|
|
Step 4
|
Perform a system restart by entering the reload command:
|
|
Step 5
|
After the system has been restarted, you should verify the preparedness of the system to support this feature as described in the Viewing Session Recovery Status section.
|
Important: More advanced users may opt to simply insert the require session recovery command syntax into an existing configuration file using a text editor or other means, and then applying the configuration file manually. Exercise caution when doing this to ensure that this command is placed among the first few lines of any existing configuration file; it must appear before the creation of any non-local context.To disable the session recovery feature on a system, enter the no require session recovery command from the Global Configuration mode prompt.
Important: If this command is issued on an in-service system, then the system must be restarted by issuing the reload command.To determine if the system is capable of performing session recovery, when enabled, enter the show session recovery status verbose command from the Exec mode prompt.
[local]host_name# show session recovery status
[local]host_name# show session recovery status
[local]host_name# show session recovery status verbose
|
callid id
|
Displays subscriber information for the call specified by id. The call ID is an 8-byte hexadecimal number.
|
|
msid id
|
|
|
username name
|
Displays information for connections for the subscriber identified by a previously configured username. name is a sequence of alpahnumeric characters and/or wildcard characters ('$' and '*') from 1 to 127 characters in length. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as wildcard enclose them in single quotes ( ‘). For example; ‘$’.
|
